Repository navigation
spec: rename specs to issue-based IDs - #3545
Merged
Merged
Conversation
Specs are now named after their parent GitHub issue instead of a sequential number, so parallel spec PRs cannot take the same number. Headings and cross-references are updated to the new IDs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>
Contributor
PR validation — ✅ 3 passing
AI Session Checks —
|
| Status | Policy | Messages |
|---|---|---|
| ✅ Passed | secrets-detection |
- |
✅ sast-scan
| Status | Policy | Messages |
|---|---|---|
| ✅ Passed | owasp-top10-2025 |
- |
| ✅ Passed | sast |
- |
| ✅ Passed | cwe-top25 |
- |
| ✅ Passed | cwe-top26-40-cusp |
- |
Scans not applied (3)
| Scan | Reason |
|---|---|
vulnerability-scan |
no manifest/lockfile changed |
github-actions-scan |
no workflow files changed |
iac-scan |
no IaC files changed |
Security context
✅ Nothing this change touches has a recorded security-fix history.
View in Chainloop ↗ · How this works ↗
Powered by Chainloop and Chainloop Trace
This was referenced Oct 7, 2026
jiparis
approved these changes
Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Specs are now named after their parent GitHub issue (
docs/specs/issue-<number>-slug.md, heading# Spec issue-<number>: <Title>) instead of a sequential number. Parallel spec PRs kept taking the same number; an issue number is unique, so they cannot collide anymore.This PR renames the existing specs, updates their headings, and updates cross-references in other specs and in test comments. Nothing else in the specs changes.
001-attestation-repo-config.mdissue-3063-attestation-repo-config.md002-session-spec-capture.mdissue-3495-session-spec-capture.md003-spec-capture-during-session.mdissue-3515-spec-capture-during-session.md004-spec-source-role.mdissue-3531-spec-source-role.md005-pi-trace-provider.mdissue-3520-pi-trace-provider.mdNote:
002-session-spec-capture.mdhad the heading# Spec 001, a duplicate number. It now has# Spec issue-3495.Links to the old paths (for example in issues or PR comments) break after this merges.
🤖 Posted by Maximus bot (Claude Code) on behalf of @migmartri